-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates Lombok dependency and project version to 1.18.30 #180
base: master
Are you sure you want to change the base?
Updates Lombok dependency and project version to 1.18.30 #180
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe the project version could be 1.18.30.0-SNAPSHOT instead of 1.18.30.1-SNAPSHOT?
Thanks @sepe81. Co-Authored-By: Sebastian Peters <[email protected]>
I fixed that in b10621e |
@awhitford thank you for this project. Would it be possible to merge this PR and release a new version? |
@awhitford would it be possible to get your review on this? Thanks. |
I just sent Anthony an email if he can merge this PR and publish the new artifacts, or find new developers he can trust, to take over this maintenance process. Hope he responds.. |
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released Resolves Meeds-io/meeds#1932
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released Resolves Meeds-io/meeds#1932
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released Resolves Meeds-io/MIPs#91
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released Resolves Meeds-io/MIPs#91
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released Resolves Meeds-io/MIPs#91
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released Resolves Meeds-io/MIPs#91
Before this fix, we use lombok-maven-plugin version 1.18.20.0 which use lombok 1.18.20 which is not compatible with jdk21. This fix is a workaround waiting this pr to be merged : awhitford/lombok.maven#180 and a new artifact released Resolves Meeds-io/MIPs#91
Hi there. Is it possible to release this version? Because delomboking in Java 21 is important. I prefer not to fallback to maven AntRun. |
This updates the Lombok dependency to version 1.18.30 so that the plugin can support Java 21.
Closes #172.
Closes #174.
Resolves #179.
Testing
I could build the project locally and use it to build and test Google Compute Engine plugin for Jenkins.